Hi Nitrino - thanks for the PR! Just to help me understand, what's the issue with using OOS? Is there some module to support it that plugs into ex_aws or something? Might this still be a problem if OOS ended up using a region name which matched one of AWS's?

Hi @bernardd
I use ex_aws without third-party modules. It works great, as OOS API has compatibility with AWS S3.

Yes, in the future there may be a problem if Oracle adds the same name of the region as the AWS. In this case, it will be better to keep the accurate list of AWS regions or add setting the control of this logic.
But while I checked the full list of Oracle regions and there is no overlap with AWS, so I decided to just clarify the regular expression that would not make big changes to the library

Full list Oracle regions: https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm

Hey - sorry for not getting back to you sooner. Thinking about this, I wonder if a better approach might not be some config parameter that allows us to skip the check entirely. Something like default_endpoint_config: false (defaulting to true). That would allow any compatible system, even ones with identical region names, to work without issue. Does that sound like a reasonable plan?

Hey @bernardd At the moment, I do not know of compatible systems with same regions, but I think the config will still be a more correct solution.
Let me change the PR for the config?